home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
8_7_09.tro
< prev
next >
Wrap
Text File
|
1991-12-22
|
95KB
|
3,129 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright (~c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v'|.5i'
.sp 1P
.LP
8.3
\fIDelivery port\fR
.sp 9p
.RT
.PP
This paragraph defines the abstract\(hyoperations and abstract\(hyerrors
which occur at a delivery\(hyport.
.EF '% Fascicle\ VIII.7\ \(em\ Rec.\ X.411''
.OF '''Fascicle\ VIII.7\ \(em\ Rec.\ X.411 %'
.RT
.sp 1P
.LP
8.3.1
\fIAbstract\(hyoperations\fR
.sp 9p
.RT
.PP
This clause defines the following delivery\(hyport
abstract\(hyoperations:
.RT
.LP
a)
message\(hydelivery
.LP
b)
report\(hydelivery
.LP
c)
delivery\(hycontrol.
.sp 1P
.LP
8.3.1.1
\fIMessage\(hydelivery\fR
.sp 9p
.RT
.PP
The message\(hydelivery abstract\(hyoperation enables the MTS to deliver
a message to an MTS\(hyuser.
.PP
The MTS\(hyuser shall not refuse delivery of a message unless the
delivery would violate the delivery\(hycontrol restrictions then in force.
.RT
.sp 1P
.LP
8.3.1.1.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 15/X.411 lists the arguments of the message\(hydelivery
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the clause in which the argument is defined.
.RT
.sp 1P
.LP
8.3.1.1.1.1\ \ \fIMessage\(hydelivery\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains an \fBMTS\(hyidentifer\fR that distinguishes the
message from all other messages at the delivery\(hyport. It shall be generated
by the MTS, and shall have the same value as the \fBmessage\(hysubmission\(hyidentifier\fR
supplied to the originator of the message when the message was submitted.
.RT
.sp 1P
.LP
8.3.1.1.1.2\ \ \fIMessage\(hydelivery\(hytime\fR
.sp 9p
.RT
.PP
This argument contains the \fBtime\fR at which delivery occurs and at which
the MTS is relinquishing responsibility for the message. It shall be
generated by the MTS.
.PP
In the case of physical delivery, this argument indicates the \fBtime\fR
at which the PDAU has taken responsibility for printing and further delivery
of the message.
.PP
The value of this argument shall be the same as the value of the
\fBmessage\(hydelivery\(hytime\fR argument reported to the originator of
the message (see \(sc\ 8.3.1.2.1.8) in a delivery\(hyreport.
.RT
.sp 1P
.LP
8.3.1.1.1.3\ \
\fIThis\(hyrecipient\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of the recipient to whom the
message is being delivered. It shall be generated by the MTS.
.PP
The value of this argument shall be the same as the value of the
\fBactual\(hyrecipient\(hyname\fR argument reported to the originator of
the message (see \(sc\ 8.3.1.2.1.2) in a delivery\(hyreport.
.PP
The \fBthis\(hyrecipient\(hyname\fR contains the \fBOR\(hyname\fR of the
individual
recipient, it shall not contain the \fBOR\(hyname\fR of a DL.
.PP
The \fBOR\(hyname\fR of the intended\(hyrecipient (if different, and the
message has been redirected) is contained in the \fBintended\(hyrecipient\(hyname\fR
argument.
.RT
.sp 1P
.LP
8.3.1.1.1.4\ \
\fIIntended\(hyrecipient\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of the intended\(hyrecipient
of the message if the message has been redirected and the time at which
the
redirection was performed. It may be generated by the MTS. A different
value of this argument may be present for each occasion the message was
redirected.
.PP
This argument comprises an \fBoriginally\(hyintended\(hyrecipient\(hyname\fR
and an \fBintended\(hyrecipient\(hyname\fR . On the first occasion a message
is redirected, both the \fBoriginally\(hyintended\(hyrecipient\(hyname\fR
and the \fBintended\(hyrecipient\(hyname\fR
contain the \fBrecipient\(hyname\fR originally\(hyspecified by the originator
of the
message. Subsequent redirections cause further \fBrecipient\(hynames\fR
to be appended to the list of \fBintended\(hyrecipient\(hynames\fR .
.PP
The \fBintended\(hyrecipient\(hyname\fR contains the \fBOR\(hyname\fR of
an individual or DL intended\(hyrecipient and the time at which the message
was redirected to
an alternate recipient.
.bp
.RT
.ce
\fBH.T. [T15.411]\fR
.ce
TABLE\ 15/X.411
.ce
\fBMessage\(hydelivery arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIDelivery arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Message\(hydelivery\(hyidentifier
T} M 8.3.1.1.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hydelivery\(hytime M 8.3.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hysubmission\(hytime M 8.2.1.1.2.2\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIOriginator argument\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hyname M 8.2.1.1.1.1\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRecipient arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
This\(hyrecipient\(hyname M 8.3.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
Intended\(hyrecipient\(hyname C 8.3.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
Redirection\(hyreason C 8.3.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
Other\(hyrecipient\(hynames C 8.3.1.1.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
DL\(hyexpansion\(hyhistory C 8.3.1.1.1.7\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIPriority argument\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Priority C 8.2.1.1.1.8\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIConversion arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Implicit\(hyconversion\(hyprohibited
T} C 8.2.1.1.1.9\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Conversion\(hywith\(hyloss\(hyprohibited
T} C 8.2.1.1.1.10
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Converted\(hyencoded\(hyinformation\(hytypes
T} C 8.3.1.1.1.8\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIDelivery method argument\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Requested\(hydelivery\(hymethod
T} C 8.2.1.1.1.14
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIPhysical delivery arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyprohibited
T} C 8.2.1.1.1.15
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyaddress\(hyrequest
T} C 8.2.1.1.1.16
.T&
lw(114p) | cw(30p) | cw(36p) .
Physical\(hydelivery\(hymodes C 8.2.1.1.1.17
.T&
lw(114p) | cw(30p) | cw(36p) .
Registered\(hymail\(hytype C 8.2.1.1.1.18
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Recipient\(hynumber\(hyfor\(hyadvice
T} C 8.2.1.1.1.19
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyrendition\(hyattributes
T} C 8.2.1.1.1.20
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyreturn\(hyaddress
T} C 8.2.1.1.1.21
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hydelivery\(hyreport\(hyrequest
T} C 8.2.1.1.1.24
.T&
lw(114p) | lw(30p) | lw(36p) .
\fISecurity arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Originator\(hycertificate C 8.2.1.1.1.25
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hytoken C 8.2.1.1.1.26
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Content\(hyconfidentiality\(hyalgorithm\(hyidentifier
T} C 8.2.1.1.1.27
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyintegrity\(hycheck C 8.2.1.1.1.28
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Message\(hyorigin\(hyauthentication\(hycheck
T} C 8.2.1.1.1.29
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hysecurity\(hylabel C 8.2.1.1.1.30
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Proof\(hyof\(hydelivery\(hyrequest
T} C 8.2.1.1.1.32
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIContent arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Original\(hyencoded\(hyinformation\(hytypes
T} C 8.2.1.1.1.33
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hytype M 8.2.1.1.1.34
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyidentifier C 8.2.1.1.1.35
.T&
lw(114p) | cw(30p) | cw(36p) .
Content M 8.2.1.1.1.37
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 15/X.411 [T15.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.3.1.1.1.5\ \
\fIRedirection\(hyreason\fR
.sp 9p
.RT
.PP
This argument indicates the reason the message has been redirected to an
alternate\(hyrecipient. It shall be generated by the MTS on each occasion
that redirection occurs. A different value of this argument may be present
for each occasion the message is redirected.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR : the
intended\(hyrecipient of the message requested that the message be
redirected to a \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR ; the
originator of the message did not prohibit recipient\(hyreassignment (see
\(sc 8.2.1.1.1.4); the MTS redirected the message to the
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR ;
.LP
\(em
\fBoriginator\(hyrequested\(hyalternate\(hyrecipient\fR : the message could
not be delivered to the intended\(hyrecipient or
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR (if registered); the
\fBoriginator\(hyrequested\(hyalternate\(hyrecipient\fR argument identified an
alternate\(hyrecipient requested by the originator of the message; the
MTS redirected the message to the
\fBoriginator\(hyrequested\(hyalternate\(hyrecipient;
.LP
\(em
\fBrecipient\(hyMD\(hyassigned\(hyalternate\(hyrecipient\fR : the
\fBrecipient\(hyname\fR argument did not identify a recipient MTS\(hyuser; the
\fBalternate\(hyrecipient\(hyallowed\fR argument generated by the originator of
the message allowed delivery to an alternate\(hyrecipient; the MTS
redirected the message to an alternate\(hyrecipient assigned by the
recipient\(hyMD to receive such messages.
.sp 1P
.LP
8.3.1.1.1.6\ \ \fIOther\(hyrecipient\(hynames\fR
.sp 9p
.RT
.PP
This argument contains the originally\(hyspecified \fBOR\(hynames\fR of
all recipients other than those identified by the
\fBoriginally\(hyintended\(hyrecipient\(hyname\fR argument, if present, and the
\fBthis\(hyrecipient\(hyname\fR argument, if the originator of the message
requested
disclosure of other recipients (with the \fBdisclosure\(hyof\(hyrecipients\fR
argument of the message\(hysubmission abstract\(hyoperation). It may be
generated by the MTS. A different value of this argument may be present
for each originally\(hyspecified recipient other than the \fBthis\(hyrecipient\(hyname\fR
to which the message is being
delivered.
.PP
Each \fBother\(hyrecipient\(hyname\fR contains the \fBOR\(hyname\fR of
an individual
recipient or a DL.
.RT
.sp 1P
.LP
8.3.1.1.1.7\ \ \fIDL\(hyexpansion\(hyhistory\fR
.sp 9p
.RT
.PP
This argument contains the sequence of \fBOR\(hynames\fR of any DLs which
have been expanded to add recipients to the copy of the message delivered
to
the recipient and the time of each expansion. It shall be generated by
the MTS if any DL\(hyexpansion has occured.
.RT
.sp 1P
.LP
8.3.1.1.1.8\ \ \fIConverted\(hyencoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
This argument identifies the \fBencoded\(hyinformation\(hytypes\fR of the
message \fBcontent\fR after conversion, if conversion took place. It may be
generated by the MTS.
.RT
.sp 1P
.LP
8.3.1.1.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
Table 16/X.411 lists the results of the message\(hydelivery
abstract\(hyoperation, and for each result qualifies its presence and identifies
the clause in which the result is defined.
.RT
.ce
\fBH.T. [T16.411]\fR
.ce
TABLE\ 16/X.411
.ce
\fBMessage\(hydelivery results\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Result Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
T{
\fIProof of delivery results\fR
T}
.T&
lw(90p) | cw(30p) | cw(36p) .
Recipient\(hycertificate O 8.3.1.1.2.1
.T&
lw(90p) | cw(30p) | cw(36p) .
Proof\(hyof\(hydelivery C 8.3.1.1.2.2
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 16/X.411 [T16.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.3.1.1.2.1\ \
\fIRecipient\(hycertificate\fR
.sp 9p
.RT
.PP
This argument contains the \fBcertificate\fR of the recipient of the
message. It shall be generated by a trusted source
(e.g.\ certification\(hyauthority), and may be supplied by the recipient of the
message, if the originator of the message requested \fBproof\(hyof\(hydelivery\fR
(see
\(sc\ 8.2.1.1.1.32) and an asymmetric\(hyencryption\(hyalgorithm is used
to compute the \fBproof\(hyof\(hydelivery\fR .
.PP
The \fBrecipient\(hycertificate\fR may be used to convey a verified copy
of the public\(hyasymmetric\(hyencryption\(hykey (\fBsubject\(hypublic\(hykey\fR
) of the recipient of the message.
.PP
The recipient's public\(hyasymmetric\(hyencryption\(hykey may be used by the
originator of the message to validate the \fBproof\(hyof\(hydelivery\fR .
.RT
.sp 1P
.LP
8.3.1.1.2.2\ \
\fIProof\(hyof\(hydelivery\fR
.sp 9p
.RT
.PP
This argument provides the originator of the message with proof
that the message has been delivered to the recipient (to provide the proof
of delivery element\(hyof\(hyservice as defined in Recommendation\ X.400).
Depending on the encryption\(hyalgorithm used and the security\(hypolicy
in force, this argument may also provide the non\(hyrepudiation of delivery
element\(hyof\(hyservice (as
defined in Recommendation\ X.400). It shall be generated by the recipient
of the message, if the originator of the message requested \fBproof\(hyof\(hydelivery\fR
(see
\(sc\ 8.2.1.1.1.32).
.PP
The \fBproof\(hyof\(hydelivery\fR is computed using the algorith identified
by the \fBproof\(hyof\(hydelivery\(hyalgorithm\(hyidentifier\fR (an \fBalgorithm\(hyidentifier\fR
).
.PP
The \fBproof\(hyof\(hydelivery\fR contains the\fR \fBproof\(hyof\(hydelivery\(hyalgorithm\(hyidentifier\fR
, and an encrypted function (e.g.,\ a
compressed or hashed version) of the \fBproof\(hyof\(hydelivery\(hyalgorithm\(hyidentifier\fR
, the \fBdelivery\(hytime\fR , and the \fBthis\(hyrecipient\(hyname\fR
, the
\fBoriginally\(hyintended\(hyrecipient\(hyname\fR , the message \fBcontent\fR
, the
\fBcontent\(hyidentifier\fR , and the \fBmessage\(hysecurity\(hylabel\fR
of the delivered
message. Optional components are included in the \fBproof\(hyof\(hydelivery\fR
if they
are present in the delivered message. Note that the \fBproof\(hyof\(hydelivery\fR
is
computed using the clear (i.e. unencrypted) message \fBcontent\fR .
.PP
Note that receipt of this argument provides the originator of the
message with proof of delivery of the message to the recipient. Non\(hyreceipt
of this argument provides neither proof of delivery nor proof of non\(hydelivery
(unless a secure route and trusted functionality are employed).
.PP
If an asymmetric\(hyencryption\(hyalgorithm is used, the \fBproof\(hyof\(hydelivery\fR
may be computed by the recipient of the message using the recipient's
secret\(hyasymmetric\(hyencryption\(hykey. The originator of the message
may validate
the \fBproof\(hyof\(hydelivery\fR using the recipient's public asymmetric\(hyencryption\(hykey
(\fBsubject\(hypublic\(hykey\fR ) derived from the \fBrecipient\(hycertificate\fR
. An asymmetric \fBproof\(hyof\(hydelivery\fR may also provide for non\(hyrepudiation
of delivery.
.PP
If a symmetric\(hyalgorithm is used, a symmetric\(hyencryption\(hykey is
used by the recipient to compute the \fBproof\(hyof\(hydelivery\fR , and
by the originator
to validate the \fBproof\(hyof\(hydelivery\fR . Note that if a
symmetric\(hyencryption\(hy
algorithm is used then the \fBproof\(hyof\(hydelivery\fR can only provide
non repudiation of delivery if the security\(hypolicy in force provides
for the involvement of a third party acting as a notary. The means by which
the symmetric\(hyencryption\(hykey is distributed is not currently defined
by this
Recommendation.
.RT
.sp 1P
.LP
8.3.1.1.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
Table 17/X.411 lists the abstract\(hyerrors that may disrupt the
message\(hydelivery abstract\(hyoperation, and for each abstract\(hyerror
identifies the clause in which the abstract\(hyerror is defined.
.RT
.ce
\fBH.T. [T17.411]\fR
.ce
TABLE\ 17/X.411
.ce
\fBMessage\(hydelivery abstract\(hyerrors\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Abstract\(hyerror Clause
_
.T&
lw(90p) | cw(36p) .
T{
Delivery\(hycontrol\(hyviolated
T} 8.3.2.1\
.T&
lw(90p) | cw(36p) .
Security\(hyerror 8.3.2.3\
.T&
lw(90p) | cw(36p) .
T{
Unsupported\(hycritical\(hyfunction
T} 8.3.2.4\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 17/X.411 [T17.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.3.1.2
\fIReport\(hydelivery\fR
.sp 9p
.RT
.PP
The \fBreport\(hydelivery\fR abstract\(hyoperation enables the MTS to
acknowledge to the MTS\(hyuser one or more outcomes of a previous invocation of
the message\(hysubmission or probe\(hysubmission abstract\(hyoperations.
.PP
For the message\(hysubmission abstract\(hyoperation, the report\(hydelivery
abstract\(hyoperation indicates the delivery or non\(hydelivery of the
submitted
message to one or more recipients.
.PP
For the probe\(hysubmission abstract\(hyoperation, the report\(hydelivery
abstract\(hyoperation indicates whether or not a message could be delivered,
or a DL\(hyexpansion could occur, if the message were to be submitted.
.PP
A single invocation of the message\(hysubmission or probe\(hysubmission
abstract\(hyoperation may provoke several occurences of the report\(hydelivery
abstract\(hyoperation, each covering one or more intended recipients. A single
occurence of the report\(hydelivery abstract\(hyoperation may report on
both delivery and non\(hydelivery to different recipients.
.PP
An invocation of the message\(hysubmission or probe\(hysubmission
abstract\(hyoperation by one MTS\(hyuser may provoke occurences of the
report\(hydelivery abstract\(hyoperation to another MTS\(hyuser, i.e.,\
reports delivered to the owner of a\ DL.
.PP
The MTS\(hyuser shall not refuse to accept the delivery of a report
unless the delivery of the report would violate the delivery\(hycontrol
restrictions then in force.
.RT
.sp 1P
.LP
8.3.1.2.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 18/X.411 lists the arguments of the report\(hydelivery
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the clause in which the argument is defined.
.RT
.sp 1P
.LP
8.3.1.2.1.1\ \
\fISubject\(hysubmission\(hyidentifier\fR
.sp 9p
.RT
.PP
This argument contains the \fBmessage\(hysubmission\(hyidentifer\fR or the
\fBprobe\(hysubmission\(hyidentifier\fR of the subject of the report. It
shall be
supplied by the MTS.
.RT
.sp 1P
.LP
8.3.1.2.1.2\ \ \fIActual\(hyrecipient\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of a recipient of the message.
It shall be generated by the originator of the message, or by the MTS if
the
message has been redirected. A different value of this argument shall be
specified for each recipient of the subject to which this report relates.
.PP
In the case of a delivery report, the \fBactual\(hyrecipient\(hyname\fR
is the name of the actual recipient of the message, and has the same value
as the
\fBthis\(hyrecipient\(hyname\fR argument of the delivered message. In the
case of a
non\(hydelivery\(hyreport, the \fBactual\(hyrecipient\(hyname\fR is the
\fBOR\(hyname\fR of the
recipient to which the message was being directed when the reason for
non\(hydelivery was encountered.
.PP
The \fBactual\(hyrecipient\(hyname\fR may be an originally\(hyspecified
\fBrecipient\(hyname\fR , or the \fBOR\(hyname\fR of an alternate\(hyrecipient
if the message has been redirected. If the message has been redirected,
the \fBOR\(hyname\fR of the
intended\(hyrecipient is contained in the \fBintended\(hyrecipient\(hyname\fR
argument.
.PP
\fR
The \fBactual\(hyrecipient\(hyname\fR contains the \fBOR\(hyname\fR of
an individual
recipient or DL.
.RT
.sp 1P
.LP
8.3.1.2.1.3\ \
\fIOriginator\(hyand\(hyDL\(hyexpansion\(hyhistory\fR
.sp 9p
.RT
.PP
This argument contains a sequence of \fBOR\(hynames\fR and associated
times which document the history of the origin of the subject\(hymessage. This
first \fBOR\(hyname\fR in the sequence is the \fBOR\(hyname\fR of the originator
of the
subject, and the remainder of the sequence is a sequence of \fBOR\(hynames\fR
of the DLs that have been expanded in directing the subject towards the
recipient (the latter being the same as the \fBDL\(hyexpansion\(hyhistory\fR
). It shall be generated by the originating\(hyMTA of the report if any
DL\(hyexpansion has occurred on the
subject.
.PP
The \fBoriginator\(hyand\(hyDL\(hyexpansion\(hyhistory\fR contains the
\fBOR\(hyname\fR of
the originator of the subject and each DL and the time at which the associated
event occurred.
.RT
.sp 1P
.LP
8.3.1.2.1.4\ \ \fIReporting\(hyDL\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of the DL that forwarded the
report to the owner of the DL. It shall be generated by a DL\(hyexpansion\(hypoint
(an MTA) when forwarding a report to the owner of the DL, in line with the
reporting\(hypolicy of the DL.
.PP
The \fBreporting\(hyDL\(hyname\fR contains the \fBOR\(hyname\fR of the
DL forwarding
the report.
.bp
.RT
.ce
\fBH.T. [T18.411]\fR
.ce
TABLE\ 18/X.411
.ce
\fBReport\(hydelivery arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fISubject submission argument \fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Subject\(hysubmission\(hyidentifier
T} M 8.3.1.2.1.1\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIRecipient arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Actual\(hyrecipient\(hyname M 8.3.1.2.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
Intended\(hyrecipient\(hyname C 8.3.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
Redirection\(hyreason C 8.3.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Originator\(hyand\(hyDL\(hyexpansion\(hyhistory
T} C 8.3.1.2.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
Reporting\(hyDL\(hyname C 8.3.1.2.1.4\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIConversion arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Converted\(hyencoded\(hyinformation\(hytypes
T} C 8.3.1.2.1.5\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fISupplementary information arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
Supplementary\(hyinformation C 8.3.1.2.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Physical\(hyforwarding\(hyaddress
T} C 8.3.1.2.1.7\
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIDelivery arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hydelivery\(hytime C 8.3.1.2.1.8\
.T&
lw(114p) | cw(30p) | cw(36p) .
Type\(hyof\(hyMTS\(hyuser C 8.3.1.2.1.9\
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fINon\(hydelivery arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Non\(hydelivery\(hyreason\(hycode
T} C 8.3.1.2.1.10
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Non\(hydelivery\(hydiagnostic\(hycode
T} C 8.3.1.2.1.11
.T&
lw(114p) | lw(30p) | lw(36p) .
\fISecurity arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
Recipient\(hycertificate C 8.3.1.1.2.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
Proof\(hyof\(hydelivery C 8.3.1.1.2.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Reporting\(hyMTA\(hycertificate
T} C 8.3.1.2.1.12
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Report\(hyorigin\(hyauthentication\(hycheck
T} C 8.3.1.2.1.13
.T&
lw(114p) | cw(30p) | cw(36p) .
Message\(hysecurity\(hylabel C 8.2.1.1.1.30
.T&
lw(114p) | lw(30p) | lw(36p) .
\fIContent arguments\fR
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Original\(hyencoded\(hyinformation\(hytypes
T} C 8.2.1.1.1.33
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hytype C 8.2.1.1.1.34
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hyidentifier C 8.2.1.1.1.35
.T&
lw(114p) | cw(30p) | cw(36p) .
Content\(hycorrelator C 8.2.1.1.1.36
.T&
lw(114p) | cw(30p) | cw(36p) .
Returned\(hycontent C 8.3.1.2.1.14
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 18/X.411 [T18.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 5
.sp 1P
.LP
8.3.1.2.1.5\ \
\fIConverted\(hyencoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
This argument identifies the \fBencoded\(hyinformation\(hytypes\fR of the
subject\(hymessage \fBcontent\fR after conversion, if conversion took place.
For a
report on a message, this argument indicates the actual
\fBencoded\(hyinformation\(hytypes\fR of the converted message \fBcontent\fR
. For a report on a probe, this argument indicates the \fBencoded\(hyinformation\(hytypes\fR
the
subject\(hymessage \fBcontent\fR would have contained after conversion, if the
subject\(hymessage were to have been submitted. It may be generated by
the MTS. A different value of this parameter may be specified for each
recipient of the
subject to which the report relates.
.bp
.RT
.sp 1P
.LP
8.3.1.2.1.6\ \ \fISupplementary\(hyinformation\fR
.sp 9p
.RT
.PP
This argument may contain information supplied by the originator of the
report, as a printable string. It may be generated by the originating\(hyMTA
of the report or an associated access\(hyunit. A different value of this
argument may be specified for each intended recipient of the subject to
which the report relates.
.PP
\fBSupplementary\(hyinformation\fR may be used by a Teletex\(hyaccess\(hyunit
or a Teletex/Telex conversion facility. It may contain a received answer\(hyback,
Telex transmission duration, or note and received recorded message as a
printable
string.
.PP
\fBSupplementary\(hyinformation\fR may also be used by other access\(hyunits,
or by the originating\(hyMTA of the report itself, to convey printable
information to the originator of the message.
.RT
.sp 1P
.LP
8.3.1.2.1.7\ \
\fIPhysical\(hyforwarding\(hyaddress\fR
.sp 9p
.RT
.PP
This argument contains the new \fBpostal\(hyOR\(hyaddress\fR of the
physical\(hyrecipient of the message. It may be generated by the associated
PDAU of the originating\(hyMTA of the report, if the originator of the
message
requested the physical\(hyforwarding\(hyaddress of the recipient (see
\(sc\ 8.2.1.1.1.16). A different value of this argument may be specified
for each intended recipient of the subject\(hymessage to which the report
relates.
.RT
.sp 1P
.LP
8.3.1.2.1.8\ \
\fIMessage\(hydelivery\(hytime\fR
.sp 9p
.RT
.PP
This argument contains the \fBtime\fR at which the subject\(hymessage was
(or would have been) delivered to the recipient MTS\(hyuser. It shall be
generated by the MTS if the message was (or would have been) successfully
delivered. A
different value of this argument may be specified for each intended\(hyrecipient
of the subject to which the report relates.
.PP
In the case of physical delivery, this argument indicates the \fBtime\fR
at which the PDAU has taken responsibility for printing and further delivery
of the message.
.PP
If the subject\(hymessage was delivered, the value of this argument shall
be the same as the value of the \fBmessage\(hydelivery\(hytime\fR argument
of the
delivered message (see \(sc\ 8.3.1.1.1.2).
.RT
.sp 1P
.LP
8.3.1.2.1.9\ \ \fIType\(hyof\(hyMTS\(hyuser\fR
.sp 9p
.RT
.PP
This argument indicates the type of recipient MTS\(hyuser to which the
message was (or would have been) delivered. It shall be generated by the
MTS if the message was (or would have been) successfully delivered. A different
value of this argument may be specified for each intended\(hyrecipient
of the subject to which the report relates.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBpublic\fR : a UA owned by an Administration;
.LP
\(em
\fBprivate\fR : a UA owned by other than an Administration;
.LP
\(em
\fBms\fR : a message\(hystore;
.LP
\(em
\fBDL\fR : a distribution\(hylist;
.LP
\(em
\fBPDAU\fR : a physical\(hydelivery\(hyaccess\(hyunit (PDAU);
.LP
\(em
\fBphysical\(hyrecipient\fR : a physical\(hyrecipient of a PDS;
.LP
\(em
\fBother\fR : an access\(hyunit of another kind.
.sp 1P
.LP
8.3.1.2.1.10\ \
\fINon\(hydelivery\(hyreason\(hycode\fR
.sp 9p
.RT
.PP
This argument contains a code indicating the reason the delivery of the
subject\(hymessage failed (or, in the case of a probe, would have failed).
It shall be generated by the MTS if the message was (or would have been)
unsuccessfully delivered. A different value of this argument may be specified
for each intended\(hyrecipient of the subject to which the report relates.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBtransfer\(hyfailure\fR : indicates that, while the MTS was
attempting to deliver or probe delivery of the subject\(hymessage, some
communication failure prevented it from doing so;
.LP
\(em
\fBunable\(hyto\(hytransfer\fR : indicates that, due to some problem
with the subject itself, the MTS could not deliver or probe delivery
of the subject\(hymessage;
.LP
\(em
\fBconversion\(hynot\(hyperformed\fR : indicates that a conversion
necessary for the delivery of the subject\(hymessage was (or would be)
unable to be performed;
.LP
\(em
\fBphysical\(hyrendition\(hynot\(hyperformed\fR : indicates that the PDAU
was unable to physically render the subject\(hymessage;
.bp
.LP
\(em
\fBphysical\(hydelivery\(hynot\(hyperformed\fR : indicates that the PDS was
unable to physically deliver the subject\(hymessage;
.LP
\(em
\fBrestricted\(hydelivery\fR : indicates that the recipient
subscribes to the restricted\(hydelivery element\(hyof\(hyservice (as defined
in Recommendation\ X.400) which prevented (or would prevent) the
delivery of the subject\(hymessage;
.LP
\(em
\fBdirectory\(hyoperation\(hyunsuccessful\fR : indicates that the
outcome of a required directory operation was unsuccessful.
.PP
Other \fBnon\(hydelivery\(hyreason\(hycodes\fR may be specified in future
versions of this Recommendation.
.PP
Further information on the nature of the problem preventing delivery is
contained in the \fBnon\(hydelivery\(hy
\fBdiagnostic\(hycode\fR argument.
.RT
.sp 1P
.LP
8.3.1.2.1.11\ \ \fINon\(hydelivery\(hydiagnostic\(hycode\fR
.sp 9p
.RT
.PP
This argument contains a code indicating the nature of the problem which
caused delivery or probing of delivery of the subject\(hymessage to fail.
The reason for failure is indicated by the \fBnon\(hydelivery\(hyreason\(hycode\fR
argument. It may be generated by the MTS if the message was (or would have
been)
unsuccessfully delivered. A different value of this argument may be specified
for each intended\(hyrecipient of the subject to which the report relates.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBunrecognised\(hyOR\(hyname\fR : the \fBrecipient\(hyname\fR argument of the
subject does not contain an \fBOR\(hyname\fR recognised by the MTS;
.LP
\(em
\fBambiguous\(hyOR\(hyname\fR : the \fBrecipient\(hyname\fR argument of the
subject identifies more than one potential recipient (i.e.,\ is
ambiguous);
.LP
\(em
\fBMTS\(hycongestion\fR : the subject could not be progressed, due to
congestion in the MTS;
.LP
\(em
\fBloop\(hydetected\fR : the subject was detected looping within the
MTS;
.LP
\(em
\fBrecipient\(hyunavailable\fR : the recipient MTS\(hyuser was (or would
be) unavailable to take delivery of the subject\(hymessage;
.LP
\(em
\fBmaximum\(hytime\(hyexpired\fR : the maximum time for delivering the
subject\(hymessage, or performing the subject\(hyprobe, expired;
.LP
\(em
\fBencoded\(hyinformation\(hytypes\(hyunsupported\fR : the
\fBencoded\(hyinformation\(hytypes\fR of the subject\(hymessage are unsupported
by
the recipient MTS\(hyuser;
.LP
\(em
\fBcontent\(hytoo\(hylong\fR : the \fBcontent\(hylength\fR of the
subject\(hymessage is too long for the recipient MTS\(hyuser to take
delivery (exceeds the \fBdeliverable\(hymaximum\(hycontent\(hylength\fR );
.LP
\(em
\fBconversion\(hyimpractical\fR : a conversion required for the
subject\(hymessage to be delivered is impractical;
.LP
\(em
\fBimplicit\(hyconversion\(hyprohibited\fR : a conversion required for
the subject\(hymessage to be delivered has been prohibited by the
originator of the subject (see \(sc\ 8.2.1.1.1.9);
.LP
\(em
\fBimplicit\(hyconversion\(hynot\(hysubscribed\fR : a conversion required
for the subject\(hymessage to be delivered has not been subscribed to by
the recipient;
.LP
\(em
\fBinvalid\(hyarguments\fR : one or more arguments in the subject was
detected as being invalid;
.LP
\(em
\fBcontent\(hysyntax\(hyerror\fR : a syntax error was detected in the
\fBcontent\fR of the subject\(hymessage (not applicable to subject\(hyprobes);
.LP
\(em
\fBsize\(hyconstraint\(hyviolation\fR :indicates that the value of one
or more parameter(s) of the subject violated the size constraints
defined in this Recommendation, and that the MTS was not prepared to
handle the specified value(s);
.LP
\(em
\fBprotocol\(hyviolation\fR : indicates that one or more mandatory
argument(s) were missing from the subject;
.LP
\(em
\fBcontent\(hytype\(hynot\(hysupported\fR : indicates that processing of
a \fBcontent\(hytype\fR not supported by the MTS was (or would be) required
to deliver the subject\(hymessage;
.LP
\(em
\fBtoo\(hymany\(hyrecipients\fR : indicates that the MTS was (or would
be) unable to deliver the subject\(hymessage due to the number of
specified recipients of the subject\(hymessage (see \(sc\ 8.2.1.1.1.2);
.LP
\(em
\fBno\(hybilateral\(hyagreement\fR : indicates that delivery of the
subject\(hymessage required (or would require) a bilateral agreement
where no such agreement exists;
.bp
.LP
\(em
\fBunsupported\(hycritical\(hyfunction\fR : indicates that a critical
function required for the transfer or delivery of the subject\(hymessage
was not suported by the originating\(hyMTA of the report;
.LP
\(em
\fBconversion\(hywith\(hyloss\(hyprohibited\fR : a conversion required for
the subject\(hymessage to be delivered would have resulted in loss of
information; conversion with loss of information was prohibited by the
originator of the subject (see \(sc\ 8.2.1.1.1.10);
.LP
\(em
\fBline\(hytoo\(hylong\fR : a conversion required for the
subject\(hymessage to be delivered would have resulted in loss of
information because the original line length was too long;
.LP
\(em
\fBpage\(hysplit\fR : a conversion required for the subject\(hymessage
to be delivered would have resulted in loss of information because an
original page would be split;
.LP
\(em
\fBpictorial\(hysymbol\(hyloss\fR : a conversion required for the
subject\(hymessage to be delivered would have resulted in loss of
information because of a loss of one or more pictorial symbols;
.LP
\(em
\fBpunctuation\(hysymbol\(hyloss\fR : a conversion required for the
subject\(hymessage to be delivered would have resulted in loss of
information because of a loss of one or more punctuation symbols;
.LP
\(em
\fBalphabetic\(hycharacter\(hyloss\fR : a conversion required for the
subject\(hymessage to be delivered would have resulted in loss of
information because of a loss of one or more alphabetic characters;
.LP
\(em
\fBmultiple\(hyinformation\(hyloss\fR : a conversion required for the
subject\(hymessage to be delivered would have resulted in multiple loss
of information;
.LP
\(em
\fBrecipient\(hyreassignment\(hyprohibited\fR : indicates that the MTS
was (or would be) unable to deliver the subject\(hymessage because the
originator of the subject prohibited redirection to a
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR (see \(sc\ 8.2.1.1.1.4);
.LP
\(em
\fBredirection\(hyloop\(hydetected\fR : the subject\(hymessage could
not be redirected to an alternate\(hyrecipient because that recipient had
previously redirected the message (redirection\(hyloop);
.LP
\(em
\fBDL\(hyexpansion\(hyprohibited\fR : indicates that the MTS was (or
would be) unable to deliver the subject\(hymessage because the originator
of the subject prohibited the expansion of DLs (see \(sc\ 8.2.1.1.1.6);
.LP
\(em
\fBno\(hyDL\(hysubmit\(hypermission\fR : the originator of the subject (or
the DL of which this DL is a member, in the case of nested DLS) does
not have permission to submit messages to this DL;
.LP
\(em
\fBDL\(hyexpansion\(hyfailure\fR : indicates that the MTS was unable to
complete the expansion of a DL;
.LP
\(em
\fBphysical\(hyrendition\(hyattributes\(hynot\(hysupported\fR : the PDAU does
not support the physical\(hyrendition\(hyattributes requested (see
\(sc\ 8.2.1.1.1.20);
.LP
\(em
\fBundeliverable\(hymail\(hyphysical\(hydelivery\(hyaddress\(hyincorrect\fR
: the
subject\(hymessage was undeliverable because the specified recipient
\fBpostal\(hyOR\(hyaddress\fR was incorrect;
.LP
\(em
\fBundeliverable\(hymail\(hyphysical\(hydelivery\(hyoffice\(hyincorrect\(hyor\(hyinvalid\fR
:
the subject\(hymessage was undeliverable because the
physical\(hydelivery\(hyoffice identified by the specified recipient
\fBpostal\(hyOR\(hyaddress\fR was incorrect or invalid (does not exit);
.LP
\(em
\fBundeliverable\(hymail\(hyphysical\(hydelivery\(hyaddress\(hyincomplete\fR :
the subject\(hymessage was undeliverable because the specified recipient
\fBpostal\(hyOR\(hyaddress\fR was incompletely specified;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hyunknown\fR : the subject\(hymessage
was undeliverable because the recipient specified in the recipient
\fBpostal\(hyOR\(hyaddress\fR was not known at that address;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hydeceased\fR : the subject\(hymessage
was undeliverable because the recipient specified in the recipient
\fBpostal\(hyOR\(hyaddress\fR is deceased;
.LP
\(em
\fBundeliverable\(hymail\(hyorganization\(hyexpired\fR : the
subject\(hymessage was undeliverable because the recipient organization
specified in the recipient \fBpostal\(hyOR\(hyaddress\fR has expired;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hyrefused\(hyto\(hyaccept\fR : the
subject\(hymessage was undeliverable because the recipient specified in
the recipient \fBpostal\(hyOR\(hyaddress\fR refused to accept it;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hydid\(hynot\(hyclaim\fR : the
subject\(hymessage was undeliverable because the recipient specified in
the recipient \fBpostal\(hyOR\(hyaddress\fR did not collect the mail;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hychanged\(hyaddress\(hypermanently\fR
:
the subject\(hymessage was undeliverable because the recipient specified
in the recipient \fBpostal\(hyOR\(hyaddress\fR has changed address permanently
(`moved'), and forwarding was not applicable;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hychanged\(hyaddress\(hytemporarily\fR
:
the subject\(hymessage was undeliverable because the recipient specified
in the recipient \fBpostal\(hyOR\(hyaddress\fR has changed address temporarily
(`on travel'), and forwarding was not applicable;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hychanged\(hytemporary\(hyaddress\fR
: the
subject\(hymessage was undeliverable because the recipient specified in
the recipient \fBpostal\(hyOR\(hyaddress\fR had changed temporary address
(`departed'), and forwarding was not applicable;
.LP
\(em
\fBundeliverable\(hymail\(hynew\(hyaddress\(hyunknown\fR : the subject\(hymessage
was undeliverable because the recipient has moved and the recipient's
new address is unknown;
.LP
\(em
\fBundeliverable\(hymail\(hyrecipient\(hydid\(hynot\(hywant\(hyforwarding\fR
: the
subject\(hymessage was undeliverable because delivery would have required
physical\(hyforwarding which the recipient did not want;
.bp
.LP
\(em
\fBundeliverable\(hymail\(hyoriginator\(hyprohibited\(hyforwarding\fR : the
physical\(hyforwarding required for the subject\(hymessage to be delivered
has been prohibited by the originator of the subject\(hymessage (see
\(sc\ 8.2.1.1.1.15);
.LP
\(em
\fBsecure\(hymessaging\(hyerror\fR : the subject could not be progressed
because it would violate the security\(hypolicy in force;
.LP
\(em
\fBunable\(hyto\(hydowngrade\fR : the subject could not be transferred
because it could not be downgraded (see Annex\ B to
Recommendation\ X.419).
.PP
Other \fBnon\(hydelivery\(hydiagnostic\(hycodes\fR may be specified in
future versions of this Recommendation.
.sp 1P
.LP
8.3.1.2.1.12\ \
\fIReporting\(hyMTA\(hycertificate\fR
.sp 9p
.RT
.PP
This argument contains the \fBcertificate\fR of the MTA that generated
the report. It shall be generated by a trusted source
(e.g.,\ a certification\(hyauthority), and may be supplied by the reporting\(hyMTA
if a \fBreport\(hyorigin\(hyauthentication\(hycheck\fR is supplied.
.PP
The \fBreporting\(hyMTA\(hycertificate\fR may be used to convey a verified
copy of the public\(hyasymmetric\(hyencription\(hykey (\fBsubject\(hypublic\(hykey\fR
) of the
reporting\(hyMTA.
.PP
The reporting\(hyMTA's public\(hyasymmetric\(hyencryption\(hykey may be used by
the originator of the message, and any MTA through which the report is
transferred, to validate the \fBreport\(hyorigin\(hyauthentication\(hycheck\fR
.
.RT
.sp 1P
.LP
8.3.1.2.1.13\ \ \fIReport\(hyorigin\(hyauthentication\(hycheck\fR
.sp 9p
.RT
.PP
This argument provides the originator of the subject\(hymessage
(or \(hyprobe), and any other MTA through which the report is transferred,
with a means of authenticating the origin of the report (to provide the
report origin authentication element\(hyof\(hyservice as defined in Recommendation\
X.400). It may be generated by the reporting\(hyMTA if a \fBmessage\(hy\fR
(or \fBprobe\(hy\fR )
\fBorigin\(hyauthentication\(hycheck\fR was present in the subject.
.PP
The \fBreport\(hyorigin\(hyauthentication\(hycheck\fR provides proof of
the origin of the report (report origin authentication), and proof of association
between the \fBmessage\(hysecurity\(hylabel\fR and the report.
.PP
The \fBreport\(hyorigin\(hyauthentication\(hycheck\fR is computed using the
algorithm identified by the \fBreport\(hyorigin\(hyauthentication\(hyalgorithm\(hyidentifier\fR
(an \fBalgorithm\(hyidentifier\fR ).
.PP
The \fBreport\(hyorigin\(hyauthentication\(hycheck\fR contains the
\fBreport\(hyorigin\(hyauthentication\(hyalgorithm\(hyidentifier\fR , and
an asymmetrically
encrypted, hashed version of the
\fBreport\(hyorigin\(hyauthentication\(hyalgorithm\(hyidentifier\fR , the
\fBcontent\(hyidentifier\fR and \fBmessage\(hysecurity\(hylabel\fR of the
subject, and all values of the following
(per\(hyrecipient) arguments: the \fBactual\(hyrecipient\(hyname\fR , the
\fBoriginally\(hyintended\(hyrecipient\(hyname\fR , and:
.RT
.LP
\(em
for a delivery\(hyreport: the \fBmessage\(hydelivery\(hytime\fR , the
\fBtype\(hyof\(hyMTS\(hyuser\fR , and if requested by the originator of
the message
for recipients to which the report relates, the
\fBrecipient\(hycertificate\fR , and the \fBproof\(hyof\(hydelivery\fR
(not present in a
report on a probe); or
.LP
\(em
for a non\(hydelivery\(hyreport: the \fBnon\(hydelivery\(hyreason\(hycode\fR
and
\fBnon\(hydelivery\(hydiagnostic\(hycode\fR .
.PP
Optional components are included in the
\fBreport\(hyauthentication\(hycheck\fR if they are present in the report.
.PP
The \fBreport\(hyorigin\(hyauthentication\(hycheck\fR may be computed by the
reporting\(hyMTA using the reporting\(hyMTA's secret\(hyasymmetric\(hyencryption\(hykey.
The \fBreport\(hyorigin\(hyauthentication\(hycheck\fR may be validated
by the originator of the subject, and any MTA through which the report
is transferred, using the
reporting\(hyMTA's public\(hyasymmetric\(hyencryption\(hykey (\fBsubject\(hypublic\(hykey\fR
) derived from the \fBreporting\(hyMTA\(hycertificate\fR .
.PP
Future versions of this Recommendation may define other forms of
\fBreport\(hyorigin\(hyauthentication\(hycheck\fR (e.g.,\ based on
symmetric\(hyencryption\(hytechniques) which may be used by MTAs through
which the
report is transferred to authenticate the origin of the report.
.RT
.sp 1P
.LP
8.3.1.2.1.14\ \ \fIReturned\(hycontent\fR
.sp 9p
.RT
.PP
This argument contains the \fBcontent\fR of the subject\(hymessage if the
originator of the subject\(hymessage indicated that the \fBcontent\fR was
to be
returned (see \(sc\ 8.2.1.1.1.23). It shall be generated by the originator
of the message, and may be returned by the MTS (if the reporting\(hyMTA
or
originating\(hyMTA supports the return of content element\(hyof\(hyservice).
.bp
.PP
This argument may only be present if there is at least one
non\(hydelivery report in the Report\(hydelivery, and if the recipient
of the report is the originator of the subject\(hymessage (and not, for
example, the owner of a DL (see\ \(sc\ 8.3.1.2.1.4)).
.PP
This argument shall not be present if any \fBencoded\(hyinformation\(hytype\fR
conversion has been performed on the \fBcontent\fR of the subject\(hymessage.
.RT
.sp 1P
.LP
8.3.1.2.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The report\(hydelivery abstract\(hyoperation returns an empty result as
indication of success.
.RT
.sp 1P
.LP
8.3.1.2.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
Table 19/X.411 lists the abstract\(hyerrors that may disrupt the
report\(hydelivery abstract\(hyoperation, and for each abstract\(hyerror
identifies the clause in which the abstract\(hyerror is defined.
.RT
.ce
\fBH.T. [T19.411]\fR
.ce
TABLE\ 19/X.411
.ce
\fBReport\(hydelivery abstract\(hyerrors\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Abstract\(hyerror Clause
_
.T&
lw(90p) | cw(36p) .
T{
Delivery\(hycontrol\(hyviolated
T} 8.3.2.1\
.T&
lw(90p) | cw(36p) .
Security\(hyerror 8.3.2.3\
.T&
lw(90p) | cw(36p) .
T{
Unsupported\(hycritical\(hyfunction
T} 8.3.2.4\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 19/X.411 [T19.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
8.3.1.3
\fIDelivery\(hycontrol\fR
.sp 9p
.RT
.PP
The delivery\(hycontrol abstract\(hyoperation enables the MTS\(hyuser to
temporarily limit the delivery\(hyport abstract\(hyoperations that the MTS may
invoke, and the messages that the MTS may deliver to the MTS\(hyuser via the
message\(hydelivery abstract\(hyoperation.
.PP
The MTS shall hold until a later time, rather than abandon,
abstract\(hyoperations and messages presently forbidden.
.PP
The successful completion of the abstract\(hyoperation signifies that the
specified controls are now in force. These controls supersede any previously
in force, and remain in effect until the association is released, the MTS\(hyuser
re\(hyinvokes the delivery\(hycontrol abstract\(hyoperation, or the MTS\(hyuser
invokes the administration\(hyport register abstract\(hyoperation to impose
constraints more
severe than the specified controls.
.PP
The abstract\(hyoperation returns an indication of any
abstract\(hyoperations that the MTS would invoke, or any message types that the
MTS would deliver or report, were it not for the prevailing controls.
.RT
.sp 1P
.LP
8.3.1.3.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 20/X.411 lists the arguments of the delivery\(hycontrol
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the clause in which the argument is defined.
.RT
.sp 1P
.LP
8.3.1.3.1.1\ \
\fIRestrict\fR
.sp 9p
.RT
.PP
This argument indicates whether the controls on delivery\(hyport
abstract\(hyoperations are to be updated or removed. It may be generated by the
MTS\(hyuser.
.PP
This argument may have one of the following values:
.RT
.LP
\(em
\fBupdate\fR : the other arguments update the prevailing
controls;
.LP
\(em
\fBremove\fR : all temporary controls are to be removed (the
default controls registered with the MTS by means of the
administration\(hyport register abstract\(hyoperation shall apply); the
other arguments are to be ignored.
.PP
In the absence of this argument, the default \fBupdate\fR shall be
assumed.
.bp
.ce
\fBH.T. [T20.411]\fR
.ce
TABLE\ 20/X.411
.ce
\fBDelivery\(hycontrol arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Arguments Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
T{
\fIDelivery control arguments\fR
T}
.T&
lw(90p) | cw(30p) | cw(36p) .
Restrict O 8.3.1.3.1.1
.T&
lw(90p) | cw(30p) | cw(36p) .
Permissible\(hyoperations O 8.3.1.3.1.2
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Permissible\(hylowest\(hypriority
T} O 8.3.1.3.1.3
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Permissible\(hyencoded\(hyinformation\(hytypes
T} O 8.3.1.3.1.4
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Permissible\(hycontent\(hytypes
T} O 8.3.1.3.1.5
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Permissible\(hymaximum\(hycontent\(hylength
T} O 8.3.1.3.1.6
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Permissible\(hysecurity\(hycontext
T} O 8.3.1.3.1.7
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 20/X.411 [T20.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
.sp 1
8.3.1.3.1.2\ \
\fIPermissible\(hyoperations\fR
.sp 9p
.RT
.PP
This argument indicates the abstract\(hyoperations that the MTS may
invoke on the MTS\(hyuser. It may be generated by the MTS\(hyuser.
.PP
This argument may have the value \fBallowed\fR or \fBprohibited\fR for
each of the following:
.RT
.LP
\(em
\fBmessage\(hydelivery\fR : the MTS may/may not invoke the
message\(hydelivery abstract\(hyoperation; and
.LP
\(em
\fBreport\(hydelivery\fR : the MTS may/may not invoke the
report\(hydelivery abstract\(hyoperation.
.PP
Other delivery\(hyport abstract\(hyoperations are not subject to
controls, and may be invoked at any time.
.PP
In the absence of this argument, the abstract\(hyoperations that the MTS
may invoke on the MTS\(hyuser are unchanged. If there has been no previous
invocation of the delivery\(hycontrol abstract\(hyoperation on the association,
the default control registerd with the MTS by means of the administration\(hyport
Register abstract\(hyoperation shall apply.
.RT
.sp 1P
.LP
8.3.1.3.1.3\ \
\fIPermissible\(hylowest\(hypriority\fR
.sp 9p
.RT
.PP
This argument contains the \fBpriority\fR of the lowest priority
message that the MTS shall deliver to the MTS\(hyuser via the message\(hydelivery
abstract\(hyoperation. It may be generated by the MTS\(hyuser.
.PP
This argument may have one of the following values of the \fBpriority\fR
argument of the message\(hysubmission abstract\(hyoperation: \fBnormal\fR
, \fBnon\(hyurgent\fR or \fBurgent\fR .
.PP
In the absence of this argument, the \fBpriority\fR of the lowest priority
message that the MTS shall deliver to the MTS\(hyuser is unchanged. If
there has been no previous invocation of the delivery\(hycontrol abstract\(hyoperation
on the association, the default control registered with the MTS by means
of the
adminsitration\(hyport Register abstract\(hyoperation shall apply.
.RT
.sp 1P
.LP
8.3.1.3.1.4\ \ \fIPermissible\(hyencoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
This argument indicates the only \fBencoded\(hyinformation\(hytypes\fR
that shall appear in messages that the MTS shall deliver to the MTS\(hyuser
via the
message\(hydelivery abstract\(hyoperation. It may be generated by the MTS\(hyuser.
.PP
The \fBpermissible\(hyencoded\(hyinformation\(hytypes\fR specified shall
be among those allowed long\(hyterm due to a previous invocation of the
administration\(hyport register abstract\(hyoperation (\fBdeliverable\(hyencoded\(hyinformation\(hytypes\fR
).
.PP
In the absence of this argument, the
\fBpermissible\(hyencoded\(hyinformation\(hytypes\fR that the MTS may deliver
to
the MTS\(hyuser are unchanged. If there has been no previous invocation of the
delivery\(hycontrol abstract\(hyoperation on the association, the default
control
registered with the MTS by means of the administration\(hyport register
abstract\(hyoperation shall apply.
.bp
.RT
.sp 1P
.LP
8.3.1.3.1.5\ \ \fIPermissible\(hycontent\(hytypes\fR
.sp 9p
.RT
.PP
This argument indicates the only \fBcontent\(hytypes\fR that shall appear
in messages that the MTS shall deliver to the MTS\(hyuser via the message\(hydelivery
abstract\(hyoperation. It may be generated by the MTS\(hyuser.
.PP
The \fBpermissible\(hycontent\(hytypes\fR specified shall be among those
allowed long\(hyterm due to a previous invocation of the administration\(hyport
register
abstract\(hyoperation (\fBdeliverable\(hycontent\(hytypes\fR ).
.PP
In the absence of this argument, the \fBpermissible\(hycontent\(hytypes\fR
that the MTS may deliver to the MTS\(hyuser are unchanged. If there has
been no
previous invocation of the delivery\(hycontrol abstract\(hyoperation on the
association, the default control registered with the MTS by means of the
administration\(hyport register abstract\(hyoperation shall apply.
.RT
.sp 1P
.LP
8.3.1.3.1.6\ \ \fIPermissible\(hymaximum\(hycontent\(hylength\fR
.sp 9p
.RT
.PP
This argument contains the \fBcontent\(hylength\fR , in octets, of the
longest\(hycontent message that the MTS shall deliver to the MTS\(hyuser
via the
message\(hydelivery abstract\(hyoperation. It may be generated by the MTS\(hyuser.
.PP
The \fBpersmissible\(hymaximum\(hycontent\(hylength\fR shall not exceed that
allowed long\(hyterm due to a previous invocation of the administration\(hyport
register abstract\(hyoperation (\fBdeliverable\(hymaximum\(hycontent\(hylength\fR
).
.PP
In the absence of this argument, the
\fBpermissible\(hymaximum\(hycontent\(hylength\fR of a message that the
MTS may deliver to the MTS\(hyuser is unchanged. If there has been no previous
invocation of the
delivery\(hycontrol abstract\(hyoperation on the association, the default
control
registered with the MTS by means of the administration port register
abstract\(hyoperation shall apply.
.RT
.sp 1P
.LP
8.3.1.3.1.7\ \ \fIPermissible\(hysecurity\(hycontext\fR
.sp 9p
.RT
.PP
This argument temporarily limits the sensitivity of delivery\(hyport abstract\(hyoperations
(delivery\(hysecurity\(hycontext) that the MTS may invoke on the MTS\(hyuser.
It is a temporary restriction of the \fBsecurity\(hycontext\fR established
when the association was initiated (see \(sc\ 8.1.1.1.1.4). It may be generated
by the MTS\(hyuser.
.PP
The \fBpermissible\(hysecurity\(hycontext\fR comprises one or more
\fBsecurity\(hylabels\fR from the set of \fBsecurity\(hylabels\fR established
as the
\fBsecurity\(hycontext\fR when the association was established.
.PP
In the absence of this argument, the \fBsecurity\(hycontext\fR of
delivery\(hyport abstract\(hyoperations is unchanged.
.RT
.sp 1P
.LP
\fR 8.3.1.3.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
Table 21/X.411 lists the results of the delivery\(hycontrol
abstract\(hyoperation, and for each result qualifies its presence and identifies
the clause in which the result is defined.
.RT
.ce
\fBH.T. [T21.411]\fR
.ce
TABLE\ 21/X.411
.ce
\fBDelivery\(hycontrol results\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Results Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
T{
\fI\*QWaiting\*U results\fR
T}
.T&
lw(90p) | cw(30p) | cw(36p) .
Waiting\(hyoperations O 8.3.1.3.2.1
.T&
lw(90p) | cw(30p) | cw(36p) .
Waiting\(hymessages O 8.3.1.3.2.2
.T&
lw(90p) | cw(30p) | cw(36p) .
T{
Waiting\(hyencoded\(hyinformation\(hytypes
T} O 8.3.1.3.2.3
.T&
lw(90p) | cw(30p) | cw(36p) .
Waiting\(hycontent\(hytypes O 8.3.1.3.2.4
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 21/411 [T21.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.3.1.3.2.1\ \ \fIWaiting\(hyoperations\fR
.sp 9p
.RT
.PP
This result indicates the abstract\(hyoperations being held by the
MTS,and that the MTS would invoke on the MTS\(hyuser if it were not for the
prevailing controls. It may be generated by the MTS.
.PP
This result may have the value \fBholding\fR or \fBnot\(hyholding\fR for
each of the following:
.RT
.LP
\(em
\fBmessage\(hydelivery\fR : the MTS is/is not holding messages, and
would invoke the message\(hydelivery abstract\(hyoperation on the MTS\(hyuser
if it were not for the prevailing controls; and
.LP
\(em
\fBreport\(hydelivery\fR : the MTS is/is not holding reports, and
would invoke the report\(hydelivery abstract\(hyoperation on the MTS\(hyuser if
it were not for the prevailing controls.
.PP
In the absence of this result, it may be assumed that the MTS is not holding
any messages or reports for delivery due to the prevailing
controls.
.sp 1P
.LP
8.3.1.3.2.2\ \ \fIWaiting\(hymessages\fR
.sp 9p
.RT
.PP
This result indicates the kind of messages the MTS is holding for delivery
to the MTS\(hyuser, and would deliver via the message\(hydelivery
abstract\(hyoperation, if it were not for the prevailing controls. It may be
generated by the MTS.
.PP
This result may have one or more of the following values:
.RT
.LP
\(em
\fBlong\(hycontent\fR : the MTS has messages held for delivery to the
MTS\(hyuser which exceed the \fBpermissible\(hymaximum\(hycontent\(hylength\fR
control currently in force;
.LP
\(em
\fBlow\(hypriority\fR : the MTS has messages held for delivery to the
MTS\(hyuser of a lower priority than the \fBpermissible\(hylowest\(hypriority\fR
control currently in force;
.LP
\(em
\fBother\(hysecurity\(hylabels\fR : the MTS has messages held for
delivery to the MTS\(hyuser bearing \fBmessage\(hy
\fBsecurity\(hylabels\fR other than those permitted by the current security\(hycontext.
.PP
In the absence of this result, it may be assumed that the MTS is not holding
any messages for delivery to the MTS\(hyuser due to the
\fBpermissible\(hymaximum\(hycontent\(hylength\fR , \fBpermissible\(hylowest\(hypriority\fR
or
\fBpermissible\(hysecurity\(hycontext\fR controls currently in force.
.sp 1P
.LP
8.3.1.3.2.3\ \ \fIWaiting\(hyencoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
This result indicates the \fBencoded\(hyinformation\(hytypes\fR in the
\fBcontent\fR of any messages held by the MTS for delivery to the MTS\(hyuser
due to prevailing controls. It may be generated by the MTS.
.PP
In the absence of this result, the \fBencoded\(hyinformation\(hytypes\fR
of any messages held by the MTS for delivery to the MTS\(hyuser are \fBunspecified\fR
.
.RT
.sp 1P
.LP
8.3.1.3.2.4\ \ \fIWaiting\(hycontent\(hytypes\fR
.sp 9p
.RT
.PP
This result indicates the \fBcontent\(hytypes\fR of any messages held by
the MTS for delivery to the MTS\(hyuser due to prevailing controls. It
may be
generated by the MTS.
.PP
In the absence of this result, the \fBcontent\(hytypes\fR of any messages
held by the MTS for delivery to the MTS\(hyuser are \fBunspecified\fR .
.RT
.sp 1P
.LP
8.3.1.3.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
Table 22/X.411 lists the abstract\(hyerrors that may disrupt the
delivery\(hycontrol abstract\(hyoperation, and for each abstract\(hyerror
identifies the clause in which the abstract\(hyerror is defined.
.RT
.ce
\fBH.T. [T22.411]\fR
.ce
TABLE\ 22/X.411
.ce
\fBDelivery\(hycontrol abstract\(hyerrors\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Abstract\(hyerror Clause
_
.T&
lw(90p) | cw(36p) .
T{
Control\(hyviolates\(hyregistration
T} 8.3.2.2\
.T&
lw(90p) | cw(36p) .
Security\(hyerror 8.3.2.3\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 22/X.411 [T22.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.3.2
\fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
This clause defines the following delivery\(hyport
abstract\(hyerrors:
.RT
.LP
a)
delivery\(hycontrol\(hyviolated
.LP
b)
control\(hyviolates\(hyregistration
.LP
c)
security\(hyerror
.LP
d)
unsupported\(hycritical\(hyfunction.
.sp 1P
.LP
8.3.2.1
\fIDelivery\(hycontrol\(hyviolated\fR
.sp 9p
.RT
.PP
The delivery\(hycontrol\(hyviolated abstract\(hyerror reports the violation
by the MTS of a control on delivery\(hyport abstract\(hyoperations imposed
by the
MTS\(hyuser via the delivery\(hycontrol abstract\(hyoperation.
.PP
The delivery\(hycontrol\(hyviolated abstract\(hyerror has no parameters.
.RT
.sp 1P
.LP
8.3.2.2
\fIControl\(hyviolates\(hyregistration\fR
.sp 9p
.RT
.PP
The control\(hyviolates\(hyregistration abstract\(hyerror reports that
the MTS is unable to accept the controls that the MTS\(hyuser attempted
to impose on delivery\(hyport abstract\(hyoperations because they violate
existing registration
parameters.
.PP
The control\(hyviolates\(hyregistration abstract\(hyerror has no
parameters.
.RT
.sp 1P
.LP
8.3.2.3
\fISecurity\(hyerror\fR
.sp 9p
.RT
.PP
The security\(hyerror abstract\(hyerror reports that the requested
abstract\(hyoperation could not be provided by the MTS\(hyuser because it would
violate the security\(hypolicy in force.
.EF '% Fascicle\ VIII.7\ \(em\ Rec.\ X.411''
.OF '''Fascicle\ VIII.7\ \(em\ Rec.\ X.411 %'
.PP
The security\(hyerror abstract\(hyerror has the following parameters,
generated by the MTS\(hyuser:
.RT
.LP
\(em
\fBsecurity\(hyproblem\fR : an identifier for the cause of the
violation of the security\(hypolicy.
.sp 1P
.LP
8.3.2.4
\fIUnsupported\(hycritical\(hyfunction\fR
.sp 9p
.RT
.PP
The unsupported\(hycritical\(hyfunction abstract\(hyerror reports that an
argument of the abstract\(hyoperation was marked \fBcritical\(hyfor\(hydelivery\fR
(see\ \(sc\ 9.1) but is unsupported by the MTS\(hyuser.
.PP
The unsupported\(hycritical\(hyfunction abstract\(hyerror has no
parameters.
.RT
.sp 1P
.LP
8.4
\fIAdministration port\fR
.sp 9p
.RT
.PP
This section defines the abstract\(hyoperations and abstract\(hyerrors
which occur at an administration\(hyport.
.RT
.sp 1P
.LP
8.4.1
\fIAbstract\(hyoperations\fR
.sp 9p
.RT
.PP
This section defines the following administration\(hyport
abstract\(hyoperations:
.RT
.LP
a)
register
.LP
b)
change\(hycredentials.
.sp 1P
.LP
8.4.1.1
\fIRegister\fR
.sp 9p
.RT
.PP
The register abstract\(hyoperation enables an MTS\(hyuser to make
long\(hyterm changes to various parameters of the MTS\(hyuser held by the MTS
concerned with delivery of messages to the MTS\(hyuser.
.PP
Such changes remain in effect until overridden by re\(hyinvocation of the
register abstract\(hyoperation. However, some parameters may be temporarily
overridden by invocation of the delivery\(hycontrol abstract\(hyoperation.
.PP
\fINote\ 1\fR \ \(em\ This abstract\(hyoperation shall be invoked before
any other submission\(hyport, delivery\(hyport or administration\(hyport
abstract\(hyoperation may be used, or an equivalent registration by local
means shall have taken place.
.PP
\fINote\ 2\fR \ \(em\ This abstract\(hyoperation does not encompass the
standing
parameters implied by the alternate recipient allowed element\(hyof\(hyservice
and
the restricted delivery element\(hyof\(hyservice defined in Recommendation\
X.400.
The manner in which those parameters are supplied and modified are a local
matter.
.bp
.RT
.sp 1P
.LP
8.4.1.1.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 23/X.411 lists the arguments of the register
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the section in which the argument is defined.
.RT
.ce
\fBH.T. [T23.411]\fR
.ce
TABLE\ 23/X.411
.ce
\fBRegister arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(114p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(114p) | lw(30p) | lw(36p) .
T{
\fIRegistration arguments\fR
T}
.T&
lw(114p) | cw(30p) | cw(36p) .
User\(hyname O 8.4.1.1.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
User\(hyaddress O 8.4.1.1.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Deliverable\(hyencoded\(hyinformation\(hytypes
T} O 8.4.1.1.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Deliverable\(hycontent\(hytypes
T} O 8.4.1.1.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Deliverable\(hymaximum\(hycontent\(hylength
T} O 8.4.1.1.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Recipient\(hyassigned\(hyalternate\(hyrecipient
T} O 8.4.1.1.1.6\
.T&
lw(114p) | cw(30p) | cw(36p) .
User\(hysecurity\(hylabels O 8.4.1.1.1.7\
.T&
lw(114p) | lw(30p) | cw(36p) .
T{
\fIDefault delivery control arguments\fR
T} 8.4.1.1.1.8\
.T&
lw(114p) | cw(30p) | cw(36p) .
Restrict O 8.3.1.3.1.1\
.T&
lw(114p) | cw(30p) | cw(36p) .
Permissible\(hyoperations O 8.3.1.3.1.2\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Permissible\(hylowest\(hypriority
T} O 8.3.1.3.1.3\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Permissible\(hyencoded\(hyinformation\(hytypes
T} O 8.3.1.3.1.4\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Permissible\(hycontent\(hytypes
T} O 8.3.1.3.1.5\
.T&
lw(114p) | cw(30p) | cw(36p) .
T{
Permissible\(hymaximum\(hycontent\(hylength
T} O 8.3.1.3.1.6\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 23/X.411 [T23.411], p. \fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
8.4.1.1.1.1\ \ \fIUser\(hyname\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of the MTS\(hyuser, if the
\fBuser\(hyname\fR is to be changed. It may be generated by the MTS\(hyuser.
.PP
In the absence of this argument, the \fBuser\(hyname\fR of the MTS\(hyuser
remains unchanged.
.PP
An MD is not required to provide MTS\(hyusers with the ability to change
their \fBOR\(hynames\fR . If it does so, the MD may restrict that ability.
It may
prohibit certain MTS\(hyusers from changing their \fBOR\(hynames\fR , or
it may restrict the scope of the change to a locally defined subset of
the components of their \fBOR\(hynames\fR . A proposed new \fBOR\(hynames\fR
shall be rejected if it is already
assigned to another MTS\(hyuser.
.RT
.sp 1P
.LP
8.4.1.1.1.2\ \ \fIUser\(hyaddress\fR
.sp 9p
.RT
.PP
This argument contains the \fBuser\(hyaddress\fR of the MTS\(hyuser, if
it is required by the MTS and if it is to be changed. It may be generated
by the
MTS\(hyuser.
.PP
The user\(hyaddress may contain one of the following forms of address of
the MTS\(hyuser.
.RT
.LP
\(em
the \fBX.121\(hyaddress\fR and/or the \fBTSAP\(hyID\fR (transport service
access point identifier); or
.LP
\(em
the \fBPSAP\(hyaddress\fR (presentation service access point
address).
.PP
Other forms of \fBuser\(hyaddress\fR may be defined in future versions
of this Recommendation.
.PP
In the absence of this argument, the \fBuser\(hyaddress\fR of the MTS\(hyuser
(if any) remains unchanged.
.RT
.sp 1P
.LP
8.4.1.1.1.3\ \ \fIDeliverable\(hyencoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
This argument indicates the \fBencoded\(hyinformation\(hytypes\fR that the
MTS shall permit to appear in messages delivered to the MTS\(hyuser, if
they are to be changed. It may be generated by the MTS\(hyuser.
.bp
.PP
The MTS shall reject as undeliverable any message for an MTS\(hyuser for
which the MTS\(hyuser is not registered to accept delivery of all the
\fBencoded\(hyinformation\(hytypes\fR of the message. Note that the MTS\(hyuser
may register to receive the \fBundefined encoded\(hyinformation\(hytype\fR
.
Deliverable\(hyencoded\(hyinformation\(hytypes also indicates the possible
encoded\(hyinformation\(hytypes to which implicit conversion can be performed.
.PP
In the absence of this argument, the
\fBdeliverable\(hyencoded\(hyinformation\(hytypes\fR shall remain unchanged.
.RT
.sp 1P
.LP
8.4.1.1.1.4\ \ \fIDeliverable\(hycontent\(hytypes\fR
.sp 9p
.RT
.PP
This argument indicates the \fBcontent\(hytypes\fR that the MTS shall
permit to appear in messages delivered to the MTS\(hyuser, if they are to be
changed. It may be generated by the MTS\(hyuser.
.PP
The MTS shall reject as undeliverable any message for an MTS\(hyuser for
which the MTS\(hyuser is not registered to accept delivery of the \fBcontent\(hytypes\fR
of the message. Note that the MTS\(hyuser may register to receive the \fBundefined
content\(hytype\fR .
.PP
In the absence of this argument, the \fBdeliverable\(hycontent\(hytypes\fR
shall remain unchanged.
.RT
.sp 1P
.LP
8.4.1.1.1.5\ \ \fIDeliverable\(hymaximum\(hycontent\(hylength\fR
.sp 9p
.RT
.PP
This argument contains the \fBcontent\(hylength\fR , in octets, of the
longest\(hycontent message that the MTS shall permit to appear in messages
delivered to the MTS\(hyuser, if it is to be changed. It may be generated
by the MTS\(hyuser.
.PP
The MTS shall reject as undeliverable any message for an MTS\(hyuser for
which the MTS\(hyuser is not registered to accept delivery of messages
of its
size.
.PP
In the absence of this argument, the
\fBdeliverable\(hymaximum\(hycontent\(hylength\fR of messages shall remain
unchanged.
.RT
.sp 1P
.LP
8.4.1.1.1.6\ \ \fIRecipient\(hyassigned\(hyalternate\(hyrecipient\fR
.sp 9p
.RT
.PP
This argument contains the \fBOR\(hyname\fR of an alternate\(hyrecipient,
specified by the MTS\(hyuser, to which messages are to be redirected, if the
alternate\(hyrecipient is to be changed. It may be generated by the MTS\(hyuser.
A
different value of this argument may be specified for each value of
\fBuser\(hysecurity\(hylabels\fR .
.PP
If a \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR is registered and
associated with a value of \fBuser\(hysecurity\(hylabels\fR , messages
bearing a matching \fBmessage\(hysecurity\(hylabel\fR shall be redirected
to the alternate\(hyrecipient.
Messages bearing a \fBmessage\(hysecurity\(hylabel\fR for which no
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR has been registered,
shall not be
redirected to a \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR .
.PP
If a single \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR is registered,
and not associated with a value of \fBuser\(hy
\fBsecurity\(hylabels\fR , all messages
shall be redirected to the alternate\(hyrecipient.
.PP
The \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR shall contain the
\fBOR\(hyname\fR of the alternate\(hyrecipient. If the
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR contains the \fBOR\(hynames\fR
of the
MTS\(hyuser (see\ \(sc\ 8.4.1.1.1.1), no \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR
is
registered.
.PP
In the absence of this argument, the
\fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR , if any, remains
unchanged.
.RT
.sp 1P
.LP
8.4.1.1.1.7\ \ \fIUser\(hysecurity\(hylabels\fR
.sp 9p
.RT
.PP
This argument contains the \fBsecurity\(hylabels\fR of the MTS\(hyuser, if
they are to be changed. It may be generated by the MTS\(hyuser.
.PP
A \fBrecipient\(hyassigned\(hyalternate\(hyrecipient\fR may be registered
for any value of \fBuser\(hysecurity\(hylabels\fR .
.PP
In the absence of this argument, the \fBuser\(hysecurity\(hylabels\fR remain
unchanged.
.PP
Note that some security\(hypolicies may only permit the
\fBuser\(hysecurity\(hylabels\fR to be changed in this way if a secure
link is employed. Other local means of changing the \fBuser\(hysecurity\(hylabels\fR
in a secure manner may be provided.
.RT
.sp 1P
.LP
8.4.1.1.1.8\ \ \fIDefault delivery control arguments\fR
.sp 9p
.RT
.PP
The default control arguments are the same as the arguments of the delivery\(hycontrol
abstract\(hyoperation, and are defined in\ \(sc\ 8.3.1.3.1. Except for
\fBpermissible\(hysecurity\(hycontext\fR , they may be generated by the
MTS\(hyuser.
.bp
.PP
The default controls are registered as arguments of the register
abstract\(hyoperation. These defaults come into effect at the beginning of an
association, and remain in effect until they are overridden by an invocation
of the delivery\(hycontrol abstract\(hyoperation.
.PP
The default control arguments shall not admit messages whose delivery are
prohibited by the prevailing registered values of the
\fBdeliverable\(hyencoded\(hyinformation\(hytypes\fR argument, the
\fBdeliverable\(hycontent\(hytypes\fR argument or the
\fBdeliverable\(hymaximum\(hycontent\(hylength\fR argument.
.RT
.sp 1P
.LP
8.4.1.1.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The register abstract\(hyoperation returns an empty result as
indication of success.
.RT
.sp 1P
.LP
8.4.1.1.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
Table 24/X.411 lists the abstract\(hyerrors that may disrupt the
register abstract\(hyoperation, and for each abstract\(hyerror identifies
the clause in which the abstract\(hyerror is defined.
.RT
.ce
\fBH.T. [T24.411]\fR
.ce
TABLE\ 24/X.411
.ce
\fBRegister abstract\(hyerror\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Abstract\(hyerror Clause
_
.T&
lw(90p) | cw(36p) .
Register\(hyrejected 8.4.2.1\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 24/X.411 [T24.411], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
8.4.1.2
\fIChange\(hycredentials\fR
.sp 9p
.RT
.PP
The change\(hycredentials abstract\(hyoperation enables the MTS\(hyuser
to change the MTS\(hyuser's \fBcredentials\fR held by the MTS, or enables
the MTS to
change the MTS's \fBcredentials\fR held by the MTS\(hyuser.
.PP
The \fBcredentials\fR are exchanged during the establishment of an
association for the mutual authentication of identity of the MTS\(hyuser
and the MTS.
.PP
The successful completion of the abstract\(hyoperation signifies that the
\fBcredentials\fR have been changed.
.PP
The disruption of the abstract\(hyoperation by an abstract\(hyerror
indicates that the \fBcredentials\fR have not been changed, either because
the old \fBcredentials\fR were incorrectly specified or that the new \fBcredentials\fR
are
unacceptable.
.RT
.sp 1P
.LP
8.4.1.2.1\ \ \fIArguments\fR
.sp 9p
.RT
.PP
Table 25/X.411 lists the arguments of the change\(hycredentials
abstract\(hyoperation, and for each argument qualifies its presence and
identifies the clause in which the argument is defined.
.RT
.ce
\fBH.T. [T25.411]\fR
.ce
TABLE\ 25/X.411
.ce
\fBChange\(hycredentials arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(30p) | cw(36p) .
Argument Presence Clause
_
.T&
lw(90p) | lw(30p) | lw(36p) .
T{
\fICredential arguments\fR
T}
.T&
lw(90p) | cw(30p) | cw(36p) .
Old\(hycredentials M 8.4.1.2.1.1
.T&
lw(90p) | cw(30p) | cw(36p) .
New\(hycredentials M 8.4.1.2.1.2
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 25/X.411 [T25.411], p. \fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.4.1.2.1.1\ \
\fIOld\(hycredentials\fR
.sp 9p
.RT
.PP
This argument contains the current (old) \fBcredentials\fR of the
invoker of the abstract\(hyoperation, held by the performer of the
abstract\(hyoperation. It shall be generated by the invoker of the
abstract\(hyoperation.
.PP
If only simple\(hyauthentication is used, the \fBcredentials\fR comprise a
simple \fBpassword\fR associated with the \fBuser\(hyname\fR , or \fBMTA\(hyname\fR
, of the
invoker.
.PP
If strong\(hyauthentication is used, the \fBcredentials\fR comprise the
\fBcertificate\fR of the invoker, generated by a trusted source (e.g.\ a
certification\(hyauthority), and supplied by the invoker.
.RT
.sp 1P
.LP
8.4.1.2.1.2\ \
\fINew\(hycredentials\fR
.sp 9p
.RT
.PP
This argument contains the proposed new \fBcredentials\fR of the
invoker of the abstract\(hyoperation, to be held by the performer of the
abstract\(hyoperation. It shall be generated by the invoker of the
abstract\(hyoperation.
.PP
The \fBnew\(hycredentials\fR shall be of the same type (i.e. simple or
strong) as the \fBold\(hycredentials\fR , as defined in\ \(sc\ 8.4.1.2.1.1.
.RT
.sp 1P
.LP
8.4.1.2.2\ \ \fIResults\fR
.sp 9p
.RT
.PP
The change\(hycredentials abstract\(hyoperation returns an empty result
as indication of success.
.RT
.sp 1P
.LP
8.4.1.2.3\ \ \fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
Table 26/X.411 lists the abstract\(hyerros that may disrupt the
change\(hycredentials abstract\(hyoperation, and for each abstract\(hyerror
identifies the paragraph in which the abstract\(hyerror is defined.
.RT
.ce
\fBH.T. [T26.411]\fR
.ce
TABLE\ 26/X.411
.ce
\fBChange\(hycredentials abstract\(hyerrors\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(90p) | cw(36p) .
Abstract\(hyerror Clause
_
.T&
lw(90p) | cw(36p) .
T{
New\(hycredentials\(hyunacceptable
T} 8.4.2.2\
.T&
lw(90p) | cw(36p) .
T{
Old\(hycredential\(hyincorrectly\(hyspecified
T} 8.4.2.3\
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 26/X.411 [T26.411], p. \fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
8.4.2
\fIAbstract\(hyerrors\fR
.sp 9p
.RT
.PP
This section defines the following administration\(hyport
abstract\(hyerrors:
.RT
.LP
a)
register\(hyrejected
.LP
b)
new\(hycredentials\(hyunacceptable
.LP
c)
old\(hycredentials\(hyincorrectly\(hyspecified.
.sp 1P
.LP
8.4.2.1
\fIRegister\(hyrejected\fR
.sp 9p
.RT
.PP
The register\(hyrejected abstract\(hyerror reports that the requested
parameters cannot be registered because one or more are improperly specified.
.PP
The register\(hyrejected abstract\(hyerror has no parameters.
.RT
.sp 1P
.LP
8.4.2.2
\fINew\(hycredentials\(hyunacceptable\fR
.sp 9p
.RT
.PP
The new\(hycredentials\(hyunacceptable abstract\(hyerror reports that the
\fBcredentials\fR cannot be changed because the \fBnew\(hycredentials\fR are
unacceptable.
.PP
The new\(hycredentials\(hyunacceptable abstract\(hyerror has no
parameters.
.bp
.RT
.sp 1P
.LP
8.4.2.3
\fIOld\(hycredentials\(hyincorrectly\(hyspecified\fR
.sp 9p
.RT
.PP
The old\(hycredentials\(hyincorrectly\(hyspecified abstract\(hyerror reports
that the \fBcredentials\fR cannot be changed because the current (\fBold\(hy\fR
)
\fBcredentials\fR were incorrectly specified.
.PP
The old\(hycredentials\(hyspecified abstract\(hyerror has no parameters.
.RT
.sp 1P
.LP
8.5
\fICommon parameter types\fR
.sp 9p
.RT
.PP
This clause defines a number of common parameter types of the MTS abstract
service.
.RT
.sp 1P
.LP
8.5.1
\fIMTS\(hyidentifier\fR
.sp 9p
.RT
.PP
\fBMTS\(hyidentifiers\fR are assigned by the MTS to distinguish between
messages and probes at the MTS abstract service, and between messages,
probes and reports within the MTS.
.PP
The \fBMTS\(hyidentifier\fR assigned to a message at a submission\(hyport
(\fBmessage\(hysubmission\(hyidentifier\fR ) is identical to the corresponding
\fBmessage\(hyidentifier\fR at a transfer\(hyport and corresponding
\fBmessage\(hydelivery\(hyidentifier\fR at a delivery\(hyport. Similarly, the
\fBMTS\(hyidentifier\fR assigned to a probe at a submission\(hyport
(\fBprobe\(hysubmission\(hyidentifier\fR ) is identical to the corresponding
\fBprobe\(hyidentifier\fR at a transfer\(hyport. \fBMTS\(hyidentifiers\fR
are also assigned to reports at transfer\(hyports (\fBreport\(hyidentifier\fR
).
.PP
An \fBMTS\(hyidentifier\fR comprises:
.RT
.LP
\(em
a \fBlocal\(hyidentifier\fR assigned by the MTA, which unambiguously
identifies the related event within the MD;
.LP
\(em
the \fBglobal\(hydomain\(hyidentifier\fR of the MD, which ensures that
the \fBMTS\(hyidentifier\fR is unambiguous throughout the MTS.
.sp 1P
.LP
8.5.2
\fIGlobal\(hydomain\(hyidentifier\fR
.sp 9p
.RT
.PP
A \fBglobal\(hydomain\(hyidentifier\fR unambiguously identifies an MD within
the MHS.
.PP
A \fBglobal\(hydomain\(hyidentifier\fR is used to ensure that an
\fBMTS\(hyidentifier\fR is unambiguous throughout the MTS, and for identifying
the
source of a \fBtrace\(hyinformation\(hyelement.\fR
.PP
In the case of an ADMD, a \fBglobal\(hydomain\(hyidentifier\fR consists
of the \fBcountry\(hyname\fR and the \fBadministration\(hydomain\(hyname\fR
of the MD. For a PRMD, it consists of the \fBcontry\(hyname\fR and the
\fBadministration\(hydomain\(hyname\fR of the
associated ADMD, plus a \fBprivate\(hydomain\(hyidentifier\fR . The
\fBprivate\(hydomain\(hyidentifier\fR is a unique identification of the
PRMD, and may be identical to the PRMD's \fBprivate\(hydomain\(hyname\fR
. As a national matter, this
identification may be either relative to the country denoted by the
\fBcountry\(hyname\fR or relative to the associated ADMD.
.PP
\fINote\ 1\fR \ \(em\ The distinction between \fBprivate\(hydomain\(hyidentifier\fR
and
\fBprivate\(hydomain\(hyname\fR has been retained for backward compatibility
with
Recommendation\ X.411 (1984). Often they will be identical.
.PP
\fINote\ 2\fR \ \(em\ In the \fBglobal\(hydomain\(hyidentifier\fR of a
PRMD, the
\fBadministration\(hydomain\(hyname\fR of the associated ADMD is optional
ISO/IEC\ 10021\(hy4.
.RT
.sp 1P
.LP
8.5.3
\fIMTA\(hyname\fR
.sp 9p
.RT
.PP
An \fBMTA\(hyname\fR is an identifier for an MTA that uniquely identifies
the MTA within the MD to which it belongs.
.RT
.sp 1P
.LP
8.5.4
\fITime\fR
.sp 9p
.RT
.PP
A \fBtime\fR parameter is specified in terms of UTC (Coordinated
Universal Time), and may optionally also contain an offset to UTC to convey
the local time. The precision of the time of day is to either one second
or one
minute, determined by the generator of the parameter.
.RT
.sp 1P
.LP
8.5.5
\fIOR\(hyname\fR
.sp 9p
.RT
.PP
An \fBOR\(hyname\fR identifies the originator or recipient of a message
according to the principles of naming and addressing described in
Recommendation\ X.402.
.bp
.PP
At a submission\(hyport, an \fBOR\(hyname\fR comprises an \fBOR\(hyaddress\fR
, or a
\fBdirectory\(hyname\fR , or both (\fBOR\(hyaddress\(hyand\(hyor\(hydirectory\(hyname\fR
). At all other
types of port, an \fBOR\(hyname\fR comprises an \fBOR\(hyaddress\fR and,
optionally,
\fBdirectory\(hyname (OR\(hyaddress\(hyand\(hyoptional\(hydirectory\(hyname)\fR
. A \fBdirectory\(hyname\fR and an \fBOR\(hyaddress\fR may each denote
an individual originator or recipient, or a DL.
.PP
A \fBdirectory\(hyname\fR is as defined in Recomendation\ X.501. The MTS
uses the \fBdirectory\(hyname\fR only when the \fBOR\(hyaddress\fR is absent
or invalid.
.PP
An \fBOR\(hyaddress\fR comprises a number of \fBstandard\(hyattributes\fR ,
optionally a number of \fBextension\(hyattributes\fR , and optionally a
number of
attributes defined by the MD to which the originator/recipient subscribes
(\fBdomain\(hydefined\(hyattributes\fR ).
.PP
The \fBstandard\(hy\fR and \fBextension\(hyattributes\fR used in an \fBOR\(hyaddress\fR
are selected from those defined in Recommendation\ X.402. Only those combinations
of attributes explicitly defined in Recommendation\ X.402 can be used to
form a
valid \fBOR\(hyaddress\fR .
.RT
.sp 1P
.LP
8.5.6
\fIEncoded\(hyinformation\(hytypes\fR
.sp 9p
.RT
.PP
The \fBencoded\(hyinformation\(hytypes\fR of a message are the kind(s) of
information that appear in its \fBcontent\fR . Both basic
\fBencoded\(hyinformation\(hytypes\fR and externally\(hydefined \fBencoded\(hyinformation\(hytypes\fR
may be specified, otherwise the \fBencoded\(hyinformation\(hytypes\fR of
a message are
unspecified.
.PP
Externally\(hydefined \fBencoded\(hyinformation\(hytypes\fR are those to which
object\(hyidentifiers are allocated by an appropriate authority. They include
both standardised and private\(hydefined \fBencoded\(hyinformation\(hytypes\fR
.
.PP
The basic \fBencoded\(hyinformation\(hytypes\fR are those originally specified
in the Recommendation\ X.411 (1984). The \fBundefined\fR type is any type
other than the specified externally\(hydefined \fBencoded\(hyinformation\(hytypes\fR
and other than the following types. The \fBtelex\fR type is defined in
Recommendation\ F.1. The
\fBia5\(hytext\fR (teleprinter) type is defined in Recommendation\ T.50. The
\fBg3\(hyfacsimile\fR type is defined in Recommendations\ T.4 and T.30. The
\fBg4\(hyclass\(hy1\fR type is defined in Recommendations\ T.5, T.6, T.400
and T.503. The \fBteletex\fR type is defined in Recommendations\ F.200,
T.61 and T.60. The
\fBvideotex\fR type is defined in Recommendations\ T.100 and T.101. The
\fBsimple\(hyformattable\(hydocument (sfd)\fR type is defined in Recommendation\
X.420
(1984) (Note that SFDs are no longer defined in any\ 1988 Recommendation).
The \fBmixed\(hymode\fR type is defined in Recommendations\ T.400 and\
T.501.
.PP
\fBNon\(hybasic\(hyparameters\fR are defined for the \fBg3\(hyfacsimile,
teletex,
g4\(hyclass\(hy1\fR and \fBmixed\(hymode\fR basic \fBencoded\(hyinformation\(hytypes\fR
for backwards
compatibility with the Recommendation\ X.411 (1984) only. It is
recommended that for each required combination of a basic
\fBencoded\(hyinformation\(hytype\fR and a specific set of \fBnon\(hybasic\(hyparameters\fR
, an
externally\(hydefined \fBencoded\(hyinformation\(hytype\fR be defined and
used in
preference.
.PP
Note that \fBnon\(hybasic parameters\fR are likely to be removed from a
future version of this Recommendation.
.PP
The \fBnon\(hybasic\(hyparameters\fR for \fBg3\(hyfacsimile\fR correspond
to the three\(hy or four\(hyoctet Facsimile Information Field (FIF) conveyed
by the Digital Command Signal (DCS) defined in Recommendation\ T.30. The
parameters are:
\fBtwo\(hydimensional, fine\(hyresolution, unlimited\(hylength, b4\(hylength,
a3\(hywidth,
b4\(hywidth\fR and \fBuncompressed\fR .
.PP
The \fBnon\(hybasic\(hyparameters\fR for \fBteletex\fR correspond to the
non\(hybasic terminal capability conveyed by the Command Document Start
(CDS) defined in
Recommendation\ T.62. The parameters are: optional \fBgraphic\(hy
\fBcharacter\(hysets\fR , optional \fBcontrol\(hycharacter\(hysets\fR ,
optional \fBpage\(hyformats\fR , optional
\fBmiscellaneous\(hyterminal\(hycapabilities\fR , and a \fBprivate\(hyuse\fR
parameter.
.PP
The \fBnon\(hybasic\(hyparameters\fR for the \fBg4\(hyclass\(hy1\fR and
\fBmixed\(hymode\fR types specify optional resolution, optional graphic
character sets, optional control character sets, and so on, which correspond
to the parameters of the
\fBpresentation\(hycapabilities\fR defined in Recommendations\ T.400, and T.503
and\ T.501.
.PP
Where \fBnon\(hybasic\(hyparameters\fR are indicated, these parameters
represent the logical `OR' of the \fBnon\(hybasic\(hyparameters\fR of each
instance on the
\fBencoded\(hyinformation\(hytype\fR in a message \fBcontent\fR . Thus,
this parameter only
serves to indicate whether there is \fBencoded\(hyinformation\(hytype\fR
compatibility, or whether conversion is required. If conversion is required,
the message
\fBcontent\fR shall be inspected to determine which \fBnon\(hybasic\(hyparameters\fR
apply to any instance of the \fBencoded\(hyinformation\(hytype\fR .
.RT
.sp 1P
.LP
8.5.7
\fICertificate\fR
.sp 9p
.RT
.PP
A \fBcertificate\fR may be used to convey a verified copy of the
public\(hyasymmetric\(hyencryption\(hykey of the subject of the \fBcertificate\fR
.
.bp
.PP
A \fBcertificate\fR contains the following parameters:
.RT
.LP
\(em
\fBsignature\(hyalgorithm\(hyidentifier\fR : an \fBalgorithm\(hyidentifier\fR
for the algorithm used by the certification\(hyauthority that issued the
\fBcertificate\fR to compute the \fBsignature\fR ;
.LP
\(em
\fBissuer\fR : the \fBdirectory\(hyname\fR of the certification\(hyauthority
that issued the \fBcertificate\fR ;
.LP
\(em
\fBvalidity\fR : a date and time of day before which the
\fBcertificate\fR should not be used, and a date and time of day after
which the
\fBcertificate\fR should not be relied upon;
.LP
\(em
\fBsubject\fR : the \fBdirectory\(hyname\fR of the subject of the
\fBcertificate\fR ;
.LP
\(em
\fBsubject\(hypublic\(hykeys\fR : one or more
public\(hyasymmetric\(hyencryption\(hykeys of the subject (each used in
conjunction with an \fBalgorithm\fR and a secret\(hyasymmetric\(hyencryption\(hykey
of the subject);
.LP
\(em
\fBalgorithms\fR : one or more \fBalgorithm\(hyidentifiers\fR , each
associated with a \fBsubject\(hypublic\(hykey\fR ;
.LP
\(em
\fBsignature\fR : an asymmetrically encrypted, hashed version of the
above parameters computed by the certification\(hyauthority that issued
the
\fBcertificate\fR using the algorithm identified by the
\fBsignature\(hy
\fBalgorithm\(hyidentifier\fR and the certification\(hyauthority's
secret\(hyasymmetric\(hyencryption\(hykey.
.PP
If the originator and a recipient of a \fBcertificate\fR are served by
the same certification\(hyauthority, the recipient may use the
certification\(hyauthority's public\(hyasymmetric\(hyencryption\(hykey
to validate the
\fBcertificate\fR , and derive the originator's public\(hyasymmetric\(hyencryption\(hykey
(\fBsubject\(hypublic\(hykey\fR ).
.PP
If the originator and a recipient of a \fBcertificate\fR are served by
different certification\(hyauthorities, the recipient may require a
return\(hycertification\(hypath to authenticate the originator's \fBcertificate\fR
. The \fBcertificate\fR may therefore include an associated \fBcertification\(hypath\fR
.
.PP
The \fBcertification\(hypath\fR may comprise a \fBforward\(hycertification\(hypath\fR
which includes the certificate of the certification\(hyauthority that issued
the \fBcertificate\fR , together with the certificates of all of its superior
certfication\(hyauthorities. The \fBforward\(hycertification\(hypath\fR
may also include the certificates of other certification\(hyauthorities,
cross\(hycertified by either the certification\(hyauthority that issued
the \fBcertificate\fR , or any of its superior certification\(hyauthorities.
.PP
A recipient of the \fBcertificate\fR may complete the required
return\(hycertification\(hypath between the recipient and the originator of the
\fBcertificate\fR by appending the recipient's own reverse\(hycertification\(hypath
to
the \fBforward\(hycertification\(hypath\fR supplied by the originator, at a
common\(hypoint\(hyof\(hytrust. The reverse\(hycertification\(hypath includes
the
reverse\(hycertificate of the certification\(hyauthority of the recipient
of the
\fBcertificate\fR , together with the reverse\(hycertificate of all of
it superior
certification\(hyauthorities. The reverse\(hycertification\(hypath may
also include the reverse\(hycertificates of other certification\(hyauthorities,
cross\(hycertified by the certification\(hyauthority of the recipient of
the \fBcertificate\fR , or any of its
superior certification authorities.
.PP
The return\(hycertification\(hypath thus formed allows the recipient of
the \fBcertificate\fR to validate each certificate in the return\(hycertification\(hypath
in turn, to derive the public\(hyasymmetric\(hyencryption\(hykey of the
certification\(hyauthority that issued the \fBcertificate\fR . The recipient
may then use the public\(hyasymmetric\(hyencryption\(hykey of the certification\(hyauthority
that
issued the \fBcertificate\fR to validate the \fBcertificate\fR , and derive the
originator's public\(hyasymmetric\(hyencryption\(hykey (\fBsubject\(hypublic\(hykey\fR
).
.PP
The form of a \fBcertificate\fR and a \fBcertification\(hypath\fR are further
defined in Recommendation\ X.509.
.PP
Future versions of this Recommendation may define other key
distribution techniques (e.g.,\ based on symmetric\(hyencryption\(hytechniques).
.RT
.sp 1P
.LP
8.5.8
\fIToken\fR
.sp 9p
.RT
.PP
A \fBtoken\fR may be used to convey to the recipient of the \fBtoken\fR
protected security\(hyrelevant information. The \fBtoken\fR provides authentication
of public security\(hyrelevant information, and confidentiality and authentication
of secret security\(hyrelevant information.
.PP
The type of a \fBtoken\fR is identified by a \fBtoken\(hytype\(hyidentifier\fR
. One type of \fBtoken\fR is currently defined by this Recommendation:
an
\fBasymmetric\(hytoken\fR . Other types of \fBtoken\fR may be defined by
future versions of this Recommendation; for example, \fBtokens\fR based
on symmetric\(hyencryption
techniques.
.bp
.PP
An \fBasymmetric\(hytoken\fR contains the following parameters:
.RT
.LP
\(em
\fBsignature\(hyalgorithm\(hyidentifier\fR : an \fBalgorithm\(hyidentifier\fR
for the algorithm used by the originator of the \fBtoken\fR to compute
the
\fBsignature\fR ;
.LP
\(em
\fBrecipient\(hyname\fR : the \fBOR address and or directory name\fR
of the intended\(hyrecipient of the \fBtoken\fR ;
.LP
\(em
\fBtime\fR : the date and time of day when the \fBtoken\fR was
generated;
.LP
\(em
\fBsigned\(hydata\fR : public security\(hyrelevant information;
.LP
\(em
\fBencryption\(hyalgorithm\(hyidentifier\fR : an \fBalgorithm\(hyidentifier\fR
for the algorithm used by the originator of the \fBtoken\fR to compute
the
\fBencrypted\(hydata\fR ;
.LP
\(em
\fBencrypted\(hydata\fR : secret security\(hyrelevant information
encrypted by the originator of the \fBtoken\fR using the algorithm identified
by
the \fBencryption\(hyalgorithm\(hyidentifier\fR and the public\(hyasymmetric\(hyencryption\(hykey
of the intended\(hyrecipient of the \fBtoken\fR ;
.LP
\(em
\fBsignature\fR : an asymmetrically encrypted, hashed version of the
above parameters computed by the originator of the \fBtoken\fR using the
algorithm identified by the \fBsignature\(hyalgorithm\(hyidentifier\fR and the
originator's secret\(hyasymmetric\(hyencryption\(hykey.
.PP
The form of a \fBtoken\fR is further defined in Recommendation\ X.509.
.sp 1P
.LP
8.5.9
\fISecurity\(hylabel\fR
.sp 9p
.RT
.PP
\fBSecurity\(hylabels\fR may be used to associate security\(hyrelevant
information with objects within the MTS.
.PP
\fBSecurity\(hylabels\fR may be assigned to an object in line with the
security\(hypolicy in force for that object. The security\(hypolicy may
also define how \fBsecurity\(hylabels\fR are to be used to enforce that
security\(hypolicy.
.PP
Within the scope of this Recommendation, \fBsecurity\(hylabels\fR may be
associated with messages, probes and reports (see\ \(sc\ 8.2.1.1.1.30),
MTS\(hyuser
(see\ \(sc\ 8.4.1.1.1.7), MDs, MTAs and associations between an MTS\(hyuser
and an
MD(or\ MTA) (see\ \(sc\ 8.1.1.1.1.4), or between MDs (or\ MTAs) (see\ \(sc\
12.1.1.1.1.4). Beyond the scope of this Recommendation, a security\(hypolicy
may, as a local
matter or by bilateral agreement, additionally assign \fBsecurity\(hylabels\fR
to
other objects within the MTS (e.g.,\ secure routes).
.PP
A \fBsecurity\(hylabel\fR comprises a set of \fBsecurity\(hyattributes\fR . The
\fBsecurity\(hyattributes\fR may include a \fBsecurity\(hypolicy\(hyidentifier\fR
, a
\fBsecurity\(hyclassification\fR , a \fBprivacy\(hymark\fR , and a set of
\fBsecurity\(hycategories\fR .
.PP
A \fBsecurity\(hypolicy\(hyidentifier\fR may be used to identify the
security\(hypolicy in force to which the \fBsecurity\(hylabel\fR relates.
.PP
If present, a \fBsecurity\(hyclassification\fR may have one of a hierarchical
list of values. The basic \fBsecurity\(hyclassification\fR hierarchy is
defined in
this Recommendation, but the use of these values is defined by the
security\(hypolicy in force. Additional values of \fBsecurity\(hyclassification\fR
, and their position in the hierarchy, may also be defined by a security\(hypolicy
as a local matter or by bilateral agreement. The basic \fBsecurity\(hyclassification\fR
hierarchy is, in ascending order: \fBunmarked, unclassified, restricted,
confidential, secret, top\(hysecret\fR .
.PP
If present, a \fBprivacy\(hymark\fR is a printable string. The content
of the printable string may be defined by a security\(hypolicy, which may
define a list of values to be used, or allow the value to be determined
by the originator of the \fBsecurity\(hylabel\fR . Examples of privacy\(hymarks
include \fB`IN CONFIDENCE'\fR and \fB`IN STRICTEST CONFIDENCE'\fR .
.PP
If present, the set of \fBsecurity\(hycategories\fR provide further
restrictions within the context of a \fBsecurity\(hyclassification\fR and/or
\fBprivacy\(hymark\fR , typically on a `need\(hyto\(hyknow' basis. The
\fBsecurity\(hycategories\fR and their values may be defined by a security\(hypolicy
as a local matter or by
bilateral agreement. Examples of possible \fBsecurity\(hycategories\fR
include caveats to the \fBsecurity\(hyclassification\fR and/or \fBprivacy\(hymark\fR
(e.g.,\ \fB`PERSONAL\(hy',
`STAFF\(hy', `COMMERCIAL\(hy'\fR , etc), closed\(hyuser\(hygroups, codewords,
etc.
.RT
.sp 1P
.LP
8.5.10
\fIAlgorithm\(hyidentifier\fR
.sp 9p
.RT
.PP
An \fBalgorithm\(hyidentifier\fR identifies an \fBalgorithm\fR and any
\fBalgorithm\(hyparameters\fR required by the \fBalgorithm\fR .
.PP
An \fBalgorithm\(hyidentifier\fR may be drawn from an international register
of algorithms, or defined by bilateral agreement.
.RT
.LP
.bp